• fmt: bad pointer in frame fmt.(*pp).printValue golang/go#64111

also ref: https://forum.golangbridge.org/t/fatal-error-invalid-pointer-found-on-stack/33579

• upgrade some types to be more meaningful for go users (for example textureID became type TextureID uint32)

I don't see this change in the PR? It's still

type TextureID struct {
	Data unsafe.Pointer
}

which is very inconvenient to work with

I don't see this change in the PR? It's still

yep, it is unsafe.Pointer but I thnk to make it uintptr instead
Would it be better?

I remember I choose unsafe.Pointer for a reason, like race tracing issue.

Yeah but this makes my feel a bit crazy.. golang/go#64111

I don't see this change in the PR? It's still

yep, it is unsafe.Pointer but I thnk to make it uintptr instead Would it be better?

Yeah, that would work, right now I'm using something like this

		ptr := unsafe.Pointer(uintptr(b.Tex.GetRef()))
		ImageV(TextureID{Data: ptr}, // ...

I remember I choose unsafe.Pointer for a reason, like race tracing issue.

How would that work? 🤔

changed to uintptr. If it compiles with -race I can merge this PR

well it doesn't compile unfortunately...
And, since GO Developers refuse to cooperate unfortunatley (AGAIN)

• see: fmt: bad pointer in frame fmt.(*pp).printValue golang/go#64111
  I see no good way at this point.

We can either use uintptr and fail each -race build or leafe texture as unsafe.pointer and suffer from the issue above...

• also ref cmd/compile: fatal error: checkptr: pointer arithmetic computed bad pointer value golang/go#64467

@gucio321 awesome! Your PR fixed not only font builder, but also clipper too. Thx a lot!

Great to hear this! I deffinitely need to finish this and merge to master!

its mostly done, now I'm getting "works for me" issue.
Gonna get back here tomorrow.

I pushed some fixes. I hope this will work soon.

@gucio321 Thanks for the effort! This PR took a while to get done, but it fixed all the problems I had workarounds for!